Fix.ensure logger set for all caplog.set level #5920
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
caplog.set_level
can conflict with other instances of caplog if the logger isn't set in the tests. This was causing the manylinux tests to fail, and would have caused the same problem if all pytests were run in the same task in the fast tests.https://github.com/wxtim/cylc/actions/runs/7501317283 (PR's with changes to Python tests only trigger the fast-tests workflow - a neat feature, but somewhat unhelpful in this particular case)
Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).?.?.x
branch.